Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update docs crd #29

Merged
merged 5 commits into from
Jan 12, 2018
Merged

Update docs crd #29

merged 5 commits into from
Jan 12, 2018

Conversation

ukclivecox
Copy link
Contributor

No description provided.


```

The predictive unit graph is a tree. Each node is of a particular type with the leaf nodes being models. If the implementation is not specified then a microservice is assumed and you must define a matching named container within the componentSpec above. Each type of PredictiveUnit has a standard set of methods it is expected to manage, see [here](../reference/seldon-deployment.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

with the leaf nodes being models. -> not necessarily but maybe we can pretend this for simplicity?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No - if we can reword it better.

* The implementation. This can be left blank if it will be a microserice as this is the default otherwise choose from the avilable appropriate implementions provided internally.
* Methods. This can be left blank if you wish to follow the standard methods for your PredictiveNode type : see [here](../reference/seldon-deployment.md).
* Endpoint. In here you should minimally if this a microservice specify whether the PredictiveUnit will use REST or gRPC. Ports will be defined automatically if not specified.
* Parameters. Specify any parameters you wish to pass to the PredictiveUnit. These will be passed as added environment variables as a JSON list of key:value pairs with the name PREDICTIVE_UNIT_PARAMETERS.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually the json list is not of key:value pairs, it has the format:

[
{
name:
value:
type:
},
... ]

@Maximophone Maximophone merged commit 0f0d24c into SeldonIO:master Jan 12, 2018
@ukclivecox ukclivecox deleted the update-docs-crd branch January 12, 2018 15:07
@ukclivecox ukclivecox mentioned this pull request Jan 12, 2018
agrski pushed a commit that referenced this pull request Dec 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants